Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix symbol IDs assigned to encoding packets #165

Merged
merged 1 commit into from
Mar 12, 2024

Conversation

mlegner
Copy link
Contributor

@mlegner mlegner commented Mar 7, 2024

Previously, we incorrectly assigned internal symbol IDs (ISIs) to the PayloadId of EncodingPackets. According to RFC 6330, it should be the encoding symbol IDs (ESIs). This commit fixes this inconsistency.

BREAKING CHANGE: As the assignment of symbol IDs changes, encoding packets generated before this change cannot be decoded by the new version and vice-versa.

Closes #164

Copy link
Owner

@cberner cberner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left one comment. Can you check that? Otherwise it looks good to me

src/encoder.rs Outdated Show resolved Hide resolved
Previously, we incorrectly assigned internal symbol IDs (ISIs) to the
`PayloadId` of `EncodingPacket`s. According to RFC 6330, it should be
the encoding symbol IDs (ESIs). This commit fixes this inconsistency.

BREAKING CHANGE: As the assignment of symbol IDs changes, encoding
packets generated before this change cannot be decoded by the new
version and vice-versa.
@cberner cberner merged commit da79ac2 into cberner:master Mar 12, 2024
2 checks passed
@mlegner mlegner deleted the fix-esi-isi branch March 12, 2024 09:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Possible inconsistency with RFC 6330: use of ISI vs ESI in PayloadId
2 participants